Method and system for configurable and scalable unmanned aerial vehicles and systems

ABSTRACT

An unmanned aircraft system (UAS) making use of unmanned aerial vehicles (UAVs) for more than one task. The inventors discovered that an improved UAS could be provided by combining one or more of these three elements: (1) hot-swappable modular kits (e.g., a plurality of components useful in UAVs to perform particular user-selectable tasks); (2) an interconnection mechanism for each component with identification protocols that provides both a physical and a data connection; and (3) an intelligent system that interprets the identification protocols and determines the configuration for a selected task, error checking, airworthiness, and calibration. The system and associated methods for the task based drone configuration and verification reduces the possibility of task failure by an operator.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional Application No.62/194,970 filed Jul. 21, 2015, which is incorporated herein byreference in its entirety.

FIELD OF THE DESCRIPTION

This description relates generally to design of an unmanned aircraft (oraerial) system (UAS) and, specifically, to the customization,configuration, and verification of components with related automaticcalibration of a UAS with unmanned aerial vehicles (UAVs) (or unmannedaircraft (UA)) for user-designated purposes.

RELEVANT BACKGROUND

Recently, there has been a rapid expansion in the production and use ofunmanned aerial vehicles (UAVs) for personal and commercial use.Further, a single UAV and its controls may be labeled or considered anunmanned aerial system (UAS), and some have labeled the UAS “autonomoussystems.” One problem with the use and further adoption of UAS is thatthe UAS (and its UAVs) is typically configured and designed for a singleuse or for a very specific purpose. Also, with such specialization, auser may require significant training to control and operate the UAS orto attempt to modify its uses (e.g., to repurpose the UAV to perform adifferent task).

Hence, there remains a need in the quickly expanding UAV (or drone)industry to provide a UAS that supports customization and configurationof its components. For many, it would be preferable if suchcustomization and configuration involved automatic calibration of a UASwith unmanned aerial vehicles (UAVs) for user-designated purposes.

In the past, such as in the design and processes described in U.S. Pat.Appl. Publ. No. 20140061377, the UAS design and associated methods havetraditionally focused on components of the UAS (e.g., its UAVs) thatwere designed for a single purpose. For example, the UAS was adapted fora particular payload lift or for overcoming a weather constraint.Problems encountered with such prior methods make UAS and UAV systemsinaccessible to many people because of the need for specific knowledge.

SUMMARY

Briefly, the present description provides a means to rapidly reconfigurea UAS to assume multiple roles without reinvestment or advancedknowledge of software and flight systems. The UAS system and associatedmethod described herein provide a unique combination of modularcomponents capable of being combined into multiple configurations forcustomized industrial, commercial, or personal applications. The UASsystem and method improve the user experience of UAS and UAVs, increasepotential applications for unmanned systems, and aid in the adoption ofthe technology and gathering of data.

One exemplary goal or purpose the inventors had in creating the new UASsystem and method was to make the UAS with associated UAVs moreversatile. The inventors discovered that an improved UAS could beprovided by combining one or more of these three (or more) elements: (1)hot-swappable modular kits (e.g., a plurality of components including:(a) cameras (such as at least one camera (a camera set) such as, but notlimited to, a remote sensing thermal, an aerial photography, a video, avisual spectrum, an infrared, or other useful camera), (b) one or moreprocessors (including, but not limited to, a CPU and/or a GPU), (c)wireless communication (e.g., I/O devices in each UAV and the UAScontroller), (d) ground control, (e) streaming devices, (f) cloudconnections, (g) data processing, (h) flight control, (i) powerdistribution, (j)motors, (k) UAV frames, (l) fuselage, (m) fins, (n)props, (o) receivers, (p) antennas, (q) sensors (including, but notlimited to, gyroscopes, accelerometers, and the like), (r) electronicspeed control, (s) power source, (t) remotes, (u) alarms, (v) vibrationsuppression, and (w) obstacle avoidance systems); (2) an interconnectionmechanism for each component (in the hot-swappable modular kit) withidentification protocols that provides both a physical and a dataconnection; and (3) an intelligent system that interprets theidentification protocols and performs the associated calibration(including, but not limited to, payload calculations, powerdistribution, flight control, range and altitude control, dataprocessing, and the like) and verification of correct installation.

More particularly, an unmanned aircraft system (UAS) is provided thatincludes an unmanned aerial vehicle (UAV). The UAS also includes aprocessor running a UAS design module (or intelligent UAS method orsoftware). The UAS includes a user input device receiving user inputindicating a selected task. The UAS includes a display device operatedby the processor to display an identifier for a UAS module determined bythe UAS design module for performing the selected task (e.g., theprocessor, input device, and display device/screen may be included in aground controller or base station in the UAS). The UAS further includesa connector associated with the UAS module, and the UAS module iscommunicatively coupled to the UAV via the connector.

In some embodiments, the UAS module includes memory storing module dataincluding an identifier of the connector and a location on the UAV forpositioning the connector. In the same or other embodiments, the UASmodule includes memory storing module data including one or more of: anidentifier of the UAS module, weight of the UAS module, powerconsumption by the UAS module, sensors included in the UAS module,number and location of connectors for attaching the UAS module to theUAV, lift provided by the UAS module, power provided by the UAS module,and mounting location for the UAS module to the UAV. In the same orother cases, the UAS module includes memory storing module dataincluding identification of the UAS module, and the UAS design moduleverifies that the UAS module is communicatively coupled to the UAV viathe connector via communications with the UAS module via the connectorbased on the identification in the memory.

In other representative implementations, the UAS design moduledetermines a second UAS module for performing the selected task (e.g.,the user-selected task or purpose for the UAS requires that the UAV havetwo (or more) modules). The second UAS module includes module data inmemory, and the module data for the UAS module and the second UAS modulefurther includes a module weight and a module-provided lift. Then, theprocessor runs an autocalibration module determining whether themodule-provided lift of the UAS module and the second UAS module isgreater at least than the weight of the UAS module and the second UASmodule and if not to display an error message on the display device.

In other cases, the UAS design module determines a second UAS module forperforming the selected task, and the second UAS module includes moduledata in memory. In this cases, though, the module data for the UASmodule and the second UAS module further includes a power consumptionvalue and a power provided value. The processor further runs anautocalibration module to determine whether the summation of the powerprovided values exceeds a summation of the power consumption values andif not to display an error message on the display device. In someinstances, the UAS design module is adapted to determine a range for theUAV with the UAS module based on module data stored in memory of the UASmodule, and the processor may operate the display device to display thedetermined range.

In these or other exemplary implementations, the UAS module comprisesone or more components from the group of: a camera, a sensor, anavigation element, a processor, a wireless communication element,memory, persistent memory storing module data, a power source, an UAVfuselage, a payload, a stabilization element, a thrust element, a liftelement, a display device, and a flight control device.

Further aspects of the description will become apparent fromconsideration of the drawings and ensuing description of preferredembodiments of the invention. A person skilled in the art will realizethat other embodiments of the invention are possible and that thedetails of the description can be modified in a number of respects, allwithout departing from the inventive concept(s). Thus, the followingdrawings and description are to be regarded as illustrative in natureand not restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

The features of the description will be better understood by referenceto the accompanying drawings which illustrate representative embodimentsof the description. In the drawings:

FIG. 1 is a block diagram illustrating one embodiment of an intelligentUAS (IUAS) system of the present description;

FIG. 2 is a block diagram illustrating one embodiment of the componentsof a hardware module for the intelligent UAS system of FIG. 1;

FIG. 3 illustrates one embodiment of physical and data connections for ascalable and customizable hardware module such as the module of FIG. 2;

FIG. 4 is a block diagram illustrating one embodiment of the scalableand customizable intelligent UAS components that may be provided in theUAS of FIG. 1;

FIG. 5 is a block diagram illustrating one embodiment of the dataassociated with a customizable module for use in a UAS such as themodule of FIG. 2;

FIG. 6 is a flow diagram illustrating one embodiment of a UASconfiguration and control method such as for use with the UAS system ofFIG. 1;

FIG. 7 is a flow diagram illustrating one embodiment of a moduleregistration method such as the module of FIG. 2;

FIG. 8 is a flow diagram illustrating one embodiment of calibration ofmodules such as the module of FIG. 2; and

FIG. 9 illustrates one embodiment of the implementation of a UAS, suchas UAS of FIG. 1, that combines customizable and scalable modules (suchas those shown in FIG. 2) into a UAV (such as the UAV of FIG. 4).

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following description provides a new task-based unmanned aerialsystem (UAS) that is specially configured with self-calibration anderror checking. One advantage of the UAS is that it combines a widearray of hardware with application-specific software (programs or codeexecuted by a processor to perform described functions) to quicklydeploy a UAS system for a purpose. In one particular, but not limiting,implementation example, the UAS includes a module or software/programs(and any additional hardware) for three dimensional (3D) scanning,another module for augmented reality (e.g., an AR module), anothermodule for real-time environmental conditioning monitoring, and soforth. Hence, the UAS system is quickly and easily configurable.

Another advantage of the described UAS is that because theapplication-specific modules are configurable, the UAS is easilyscalable and customizable from a small UAS for a single task to a largeror more complex UAS for performing multiple tasks (with tasks changingover time in some cases). This enables minimal initial hardwareinvestment and removes obstacles for UAS adoption. Furthermore, theautomatic (or “self”) calibration and error checking ensures successfulcompletion of UAS-assisted tasks.

Referring now to the figures, one preferred embodiment of theconfigurable and scalable modular UAS system 110 incorporatingtask-based design and self-calibration software is shown in FIG. 1. Theinventors discovered that UAS parts can be modified or configured toinclude knowledgeable application-specific software. With thismodification or advancement, the IUAS system (or simply the UAS) 110 ofthe various embodiments yields a quick and accurate technique fordelivering desired data and UAS applications without the need foradvanced knowledge of flight systems or UAV and UAS components.

As shown at 120 (also with reference to FIG. 4) and arrows, the UAS 110includes memory for storing a UAS task selection (or user input) thatmay be provided by a user or operator (e.g., from user 180, shown inFIG. 9) via an I/O device of the UAS 110 via I/O devices provided andmanaged by a controller (e.g., a controller 410 with one or moreprocessors and control software as shown in FIG. 4). The use orprocessing of this user task selection/user input from user 180 isdescribed in more detail below. The UAS 110 also includes modulehardware and/or network connectors 130 for receiving and/or mounting oneor more modules (such as modules 140), e.g., for connection of ahardware/software module to a UAV or the like. Such a connector 130 maybe implemented as shown with reference to FIG. 3.

Significantly, the UAS 110 also includes one or more customizable andscalable hardware modules 140. These may be implemented as shown in FIG.2. The module 140 (or modular kit) may include one or more of thefollowing components: (a) cameras (such as at least one camera (a cameraset) such as, but not limited to, a remote sensing thermal imager, anaerial photography, a video, a visual spectrum, an infrared, or otheruseful camera), (b) one or more processors (including, but not limitedto, a CPU and/or a GPU), (c) wireless communication (e.g., I/O devicesin each UAV and the UAS controller), (d) ground control, (e) streamingdevices, (f) cloud connections, (g) data processing, (h) flight control,(i) power distribution, (j) motors, (k) UAV frames, (l) fuselage, (m)fins, (n) props, (o) receivers, (p) antennas, (q) sensors (including,but not limited to, gyroscopes, accelerometers, and the like), (r)electronic speed control, (s) power source, (t) remotes, (u) alarms, (v)vibration suppression, (w) obstacle avoidance systems), (x) payload; and(y) stabilization; and (z) lift. The components of the module 140 arecoupled within the UAS (e.g., onto or to form a UAV) using theconnectors 130.

Further, the UAS 110 includes module identifying information 150 (ormemory/data storage for storing such information 150). This information150 is processed by a controller or control software of the UAS 110 asdescribed below to provide self or automated calibration of the UAS 110and error checking during assembly. The module identifying information150 may include a UAV module identifier (such as ID 515 shown in FIG. 5as part of the module data 150, which may be included in memory of thehardware module 140 shown in FIG. 2 (or as part of module 140)).

Further, the UAS 110 may include a basic UAS configuration or groundcontroller 170, which may take the form of ground controller or basestation 410 in FIG. 4, to allow a remote operator to provide user inputto the UAS 110 and/or to provide some amount of manual control over theUAS 110 (or its UAVs). The base UAS 170 may have preconfiguredcomponents, and it is an optional component in some implementations ofthe UAS 110. 170 may also take the form of a common module withcomponents utilized by numerous configurations of a UAS (e.g. thrust,power, fuselage, communication, ground control).

FIG. 2 details one preferred embodiment of an intelligent UAS scalableand customizable hardware module 140 (or hot-swappable modular kit). Themodule 140 is comprised of, but not limited to, hardware components 285and software (or data) components 290. The hardware components 285 areshown to include: a camera(s) 205 (e.g. for remote sensing, opticalsensor packages (cameras), infrared (IR) cameras, and electro-optical(EO) cameras, aerial photography (at different resolutions), video,visual spectrum, and infrared imaging); sensors 210 (e.g. multi-usesensors to minimize swapping, motion, ultrasonic, magnetic field,accelerometer, gyroscope, optic flow, laser range finders, acoustic,synthetic vision, thermal imaging, RADAR); navigation 215; aprocessor(s) 220 (e.g. one or more CPUs, GPUs, FPGAs, specializedprocessors, or other processors for data processing); communicationelements 225; memory 230 (e.g. volatile memory such as RAM); storage 235(e.g. non-volatile memory such as solid state, flash, optical, magneticstorage (e.g., hard drives), millipede, SD cards, USB, or otheravailable storage); power 240 (e.g. one or more batteries, electricalpower, liquids such as gasoline or hydrogen, a renewable energy sourcesuch as solar or wind, may be rechargeable, or any other suitable powersource); frame 245 (e.g. fuselage, UAV frame(s), fin(s), and prop(s) andtheir specific appearance such as camouflage) ; stabilization andvibration suppression elements 250; payload 255 (e.g. dispersants,deliverables, or other payloads); a thrust device(s) 260; flight controlcomponents 265 (e.g. electronic speed control); environmental conditions270 (e.g. pressure, humidity, light, UV, temperature, wind speed, watercurrents, barometer, calorimeters, heat rate sensors, sun sensors forspaceborne operation, and other environmental sensors); safety 275 (e.g.obstacle avoidance system, proximity sensors, GPS, geofencing); groundcontrol 280 (e.g. devices or components for human control of the vehiclethat can range in complexity); and other 282 (e.g. cooling, warningalarms, USB ports). In implementing the module 140, these hardwarecomponents 285 can be combined in a plurality of arrangements rangingfrom utilizing a single one of the components to a modular kit thatincludes many-to-all components or even redundant components (e.g.,there can be multiple cameras 205, multiple sensors 210, multipleprocessors 220, and so forth, combined or omitted as necessary forselected task).

The communication component 225 may include, but is not limited to,communication devices implementing cellular, internet, Bluetooth,Ethernet, satellite, Wi-Fi, radio, transponders, and streamingapparatuses. In some embodiments, communication component 225 mayinclude wired technologies that provide a data connection such as fiberoptic and it is understood that component 225 may include other wiredand wireless technologies. The software components 290 of the module 140may include module data (or module data communication element) 150,e.g., include software/programming (which may be executed by processor220) to communicate (e.g., with communication component 225) the moduledata as shown in FIG. 5 into or within the UAS 110 (e.g., to acontroller or control module run by a processor of the UAS 110). Themethod 700 for identifying and verifying module connections may also beincluded in software components 290 (method 700 is further detailed inFIG. 7 and may be implemented by code provided as one or more of thecomponents 290).

FIG. 3 illustrates one preferred embodiment of a connector 130 that maybe provided on module 140 (e.g., to implement the connector 130 shown inFIG. 1). The connector 130 is configured to provide physical and dataconnections. As shown, the connector 130 includes guide pins 310 tomount a hardware module (e.g., module 140) and to guide data connectionwith coupling or data connector 330 into the correct location in the UAS(e.g., UAS 110 of FIG. 1). The connector 130 also includes a lockingmechanism 320 that secures connector 130 within a UAS (such as onto aUAV). In some UAS implementations, the data connector or connection 330employs a peer-to-peer network protocol while other protocols may beused in the same or other cases.

In FIG. 4, one exemplary embodiment of a UAS 110 is shown in more detailwith a functional block diagram. The scalable and customizable elementsof the UAS 110 include at least one unmanned aerial vehicle (UAV) 405and a ground controller or base station 410. The UAV 405 includes, butis not limited to, a module 140, a connector 130, a UAS readiness method800 that includes a controller and/or processor as may be provided aspart of the UAS or intelligent system 110 with software/programs toimplement the intelligent or UAS control method described herein (e.g.,the method 800 shown in FIG. 8). The ground controller 410 is shown toinclude, but is not limited to, a transmit/receive element 420, adisplay screen 425, a processor 430, a power source 435, a user inputdevice 440, memory 445, a cloud connection 450, the intelligent method600 that includes a controller and/or processor as may be provided aspart of the UAS or intelligent system 110 with software/programs toimplement the intelligent or UAS control method described herein (e.g.,as shown in FIG. 6), and other components 455. While software isillustrated as part of UAV 405 or ground control 410, it is not limitedto being executed in those locations (e.g., intelligent method 600 maybe run on a UAV or the cloud, and method 800 may also be executed in alocation other than on a UAV, such as on a user device or on the cloud).

FIG. 5 demonstrates one preferred embodiment of the module data 150 thatmay be associated with and stored in the memory (e.g., memory 230) ofmodule 140. The module data 150 is the data that is provided tointelligent UAS system 110 when a module 140 is connected via aconnector 130 to the UAS 110 (e.g., plugged into a UAV or the like asdetailed in method 700 in FIG. 7). The module data 150 is shown toinclude, but is not restricted to, weight (of the module) 505, powerconsumption (by the module's elements) 510, module identifier 515,sensors (provided in the module) 520, number of connections 525, liftprovided 530, power provided (by the module elements) 535, location(within the UAS such as location of connector on a UAV or the like forproper assembly of the UAV) 540, and other elements 550.

FIG. 6 details one useful method 600 for the operation (a UAS controlmethod) of a UAS such as the IUAS system 110 shown in FIG. 1. Theintelligent method 600 starts at 605 such as with loading controlsoftware onto a ground controller and/or in a UAV or other unmannedvehicle in a UAS for providing the functions/steps of method 600.

In step 610, a user 180 selects a desired task on display 425 usinginput 440, e.g., from a list of predefined tasks available with the UASsystem 110 (or its unmanned vehicles). The method 600 then continues at620 with the ground controller displaying on display 425 a list ofrequired modules 140 to perform the task chosen in step 610. At step630, the IUAS determines if all modules 140 required for task 140specified by the user in step 610 have been properly registered with theIUAS via the module(s) communicating with the IUAS 110 in method 700. Ifnot, step 635 is performed to repeat step 620 to display all the modules140 again and/or to inform the user that all the needed modules are notyet connected to the UAS 110 (or by displaying only the missing modules140).

The method 600 then continues after step 630 with the IUAS executingmethod 800 in step 650 to determine whether or not all the modules 140are valid to provide sufficient thrust, power, and so forth to ensurethe aircraft is ready for flight. If not determined to be valid, themethod 600 performs steps 645 in which an error code is displayed to theuser via operation of the display screen 425 and then step 620 isrepeated or executed. If the modules 140 are validated and the UAS isready for task execution, step 650 executes in the method 600 to operatethe display screen 425 to indicate that all modules 140 are valid andoperations of the UAV or other unmanned vehicles by the UAS 110 mayproceed. At step 660, the user operates the UAV/unmanned vehicle 405 viathe controller 410, and the method 600 may then continue at 610. Inmethod 600, one task is selected for execution, but it is contemplatedthat multiple tasks may be selected.

FIG. 7 demonstrates one possible method 700 executed by each module 140.Particularly, the method 700 is performed to provide, for module(s) 140,registration and communication with the intelligent UAS system 110. Asshown, the method 700 starts at 705 when the module 140 receives powereither via an on-board power switch or when connected to another module140 that provides power.

In step 710, the module 140 detects a connection with a new module 140.Then, at step 720, the module(s) 140 attempt to communicate with theIUAS 110 via a connector 330. In step 730, the method 700 involvesdetermining whether the module 140 receives a response from the UAS 110(e.g., indicating successful connection and initiating ofcommunications, possibly wireless, between the module 140 and thecontroller/controller program). Step 735 executes when step 730 failsand remains in a loop waiting until a new module is connected. When amodule 140 is connected, step 735 returns to step 720 and attempts toinitiate communication with IUAS 110.

If the module 140 receives a response from the UAS 110 as verified instep 730, the method 700 continues with performing step 740. At 740,module data 150 is transmitted to the UAS 110 via communicationconnector 330 (of the connector 130) used to couple the module 140 withthe UAS 110. The method continues to step 750 and determines if themodule 140 remains connected to the UAS 110. If step 750 fails, themethod 700 exits or ends at 755; otherwise, the method 700 continueswith step 760. Step 760 determines if the module(s) 140 receives acommand from the UAS 110 (or its controller and/or control software).Step 770 executes if step 760 is successful (message is received). Ifstep 760 fails (no message received), step 750 is executed or repeated.In step 770, the module 140 processes the UAS command. Method 700 willremain in the loop executed by step 770 as long as the module 140remains connected to the UAS 110.

FIG. 8 shows steps of one possible method 800 executed by IUAS 110 forautomatic calibration of the module 140 and determination of flightreadiness, with the method 800 starting at 805 by a call from the method600. In step 810, the UAS 110 (or its controller and control software)calculates weight of all modules 140 such as with a lookup and summationof weight values 505 in module data 150.

In step 820, the UAS 110 calculates the lift provided such as byretrieving and summing the lift provided value 530 from data module 150.In step 830, the UAS 110 determines if this lift from step 820 issufficient for the weight of UAV 405 (determined in part from calculatedweight from step 810). If step 830 fails (lift is not greater thanweight), step 835 is executed to operate the display screen 425 todisplay an error 802 to the user related to insufficient lift and themethod ends in step 897.

If the calculated lift is adequate, step 830 is successful and step 840is executed. Step 840 involves the UAS 110 calculating power consumption510 of the modules 140. In step 850, the method 800 continues with theUAS 110 calculating the power provided 535 by power sources 240 of themodule(s) 140. Step 860 involves the UAS 110 determining if the providedpower 535 is sufficient for the determined power consumption 510. Ifstep 860 fails (power is not sufficient from power sources), step 865executes with an insufficient power provided error displayed to the user(such as via operations of the display screen 425) and the method endsin step 897.

Step 870 is executed when step 860 is successful (power provided equalsor exceeds power consumption for selected task) and involves the UAS 110determining the location 540 and weight 505 of all the modules 140 todetermine airworthiness. In step 880, the UAS 110 determines thelocation from step 870 of thrust 260, lift provided 530, and liftcapabilities from step 820 for all the modules 140. Step 885 involvesdetermining if lift 530 and power provided 535 is greater than thecalculated weight from step 870 to maintain airworthiness. Step 887 isexecuted if step 885 fails, and an error is displayed to the user viaoperation of the display screen 425 and the method 800 ends in step 897.Step 890 executes if step 885 is successful, and the UAS 110 calculatesrange and altitude for the payload 250. In 895, the calculated range andaltitude from step 890 are displayed to a user on display device 425,and the method 800 ends at step 897. The steps of method 800 are notillustrated to be all inclusive and may be omitted or combined asnecessary. The determination of airworthiness and associated calibrationof the modules may be more complicated than illustrated and iscontemplated to be within the scope of the invention.

FIG. 9 illustrates a view of one possible embodiment of the componentsof an IUAS 110 including, but not restricted to, a UAV 405, groundcontrol 410, and user 180. As shown, the UAV 405 includes one or moremodules 140 connected via connectors 130. A plurality of arrangements ofthe modules 140 is possible to implement a desirable and useful UAV 405.The UAV 405 is illustrated as a quadcopter but could take a range ofaircraft forms including single copter, fixed wing aircraft, or anyother form of rotary or fixed wing aircraft or hybrids/combinationsthereof, ranging in size and complexity. While a single user, groundcontrol, and UAV are illustrated, it is contemplated that multipleusers, ground controls, UAVs and combinations or omissions thereof maybe utilized in IUAS 110.

Although some embodiments are shown to include certain features, theapplicant specifically contemplates that any feature disclosed hereinmay be used together or in combination with any other feature on anyembodiment of the invention. It is also contemplated that any featuremay be specifically excluded from any embodiment of an invention.

For example, many variations of the described UAS and associated methodswill occur to those skilled in the art. Some variations include, but arenot limited to: the use of multiple UAVs; alternate connection typesbetween modules; integration with external storage, processors,hardware, software, and the cloud; and calibration of more elements ofthe UAS such as guide, stabilization, or flight control. The range ofviewing and input devices in the UAS system is also not restrictive andcould include both mobile internet devices and non-mobile devices aswell as head-mounted viewing devices such as augmented reality (AR) orvirtual reality (VR) goggles. The UAS system can also be configured toinclude not only aircraft (UAVs) but also of autonomous motorized groundvehicles, sea craft, spacecraft, and other types of unmanned vehicles.The system can be manned with an operator or can be run autonomous. Allsuch variations are intended to be within the scope and spirit of thedescription and following claims.

With the above discussion and general discussion of an intelligent UAS(IUAS) understood, it may be useful to more specifically discussfunctions of particular components and control software of theintelligent system and the task-specific modules that comprise the UAS.

During the planning stage, an operator selects a task for completion ontheir user device, such as a smartphone. In some implementations, theuser device may be a wearable device such as a smart helmet withAugmented Reality (AR). The planning stage may also be completed on awebsite and does not yet require the user to physically possess the UAS.The user may choose tasks that range in complication from flying-for-funto specialized commercial, industrial, military, or scientific tasks. Asan illustrative example, the operator is a member of a research team atan educational institution who wishes to acquire remote sensing data tolocate ancient landscape modifications in a rainforest environment.Ancient limestone ruins in a rainforest environment alter the appearanceof overlying vegetation when viewed in color infrared (a change that isotherwise not visible to the naked eye when viewed in the visible colorspectrum). When the remote sensing task is selected, the IUAS providesthe user a list of necessary modules for task completion which mayinclude: a remote sensing module, a design module, a ground controlmodule, and a basic UAV. These modules may be comprised of packagedcomponents purchased by the archaeologist and may come pre-assembled intask-specific packages.

The IUAS software is required to coordinate all of the connectedmodules, to ensure precise operation of the IUAS including identifyingcorrect installation of modules and error checking, and to determine ifthe UAS is ready for flight. The associated software for successfulmodule connection, error checking, flight, and calibration may run onthe base UAV, ground control, executed on the user device (e.g. thesoftware may be downloaded, installed, or come pre-installed), or, insome embodiments, run external such as on the cloud. The base UAV mayinclude pre-assembled components common to a multitude of tasks (e.g.thrust, power, stabilization, communication, ground control) to quicklyrepurpose the UAS with minimal investment. A color infrared camera andassociated storage may provide the remote sensing module. A groundcontrol module may include a user device and controller to interfacewith the UAV. In some embodiments, more than one UAV (or ground control)is required and assembled for the task. In other cases, more than oneoperator may be necessary. In yet a further embodiment, more than onetask may be selected for the IUAS that uses a common configuration (orvice versa).

During assembly, each module contains module information to ensurecomponents are assembled correctly. Modules may be physically identifiedby color, markings, shapes, or other distinguishing features. Modulesare assembled in this illustrative example via a locking pin-mountsystem that provides both a physical and data connection to aid incorrect UAS assembly although alternate connections provided by amanufacturer could also be utilized. As modules are connected together,module information is passed to the IUAS to determine both if they arecommunicating correctly and if they are assembled correctly. If themodule information received by the system does not compare to thatrequired for task(s) completion, the operator is given an error thatrequires correction for UAS operation. For example, if the user fails toinstall the color infrared camera module, the selected task cannot becompleted, and an error is issued.

When assembly is correctly completed, aided by the IUAS, the system isprepared for flight. During preflight, the IUAS automatically calibratesall components to aid in successful task completion. For example, itcalculates if the range of the UAV is sufficient to acquire the remotesensing data and successfully return home based on the powerconsumption, environmental conditions, performs stabilization, andcalculates aircraft weight. Furthermore, the system ensures all systemsare ready for flight and the UAV is airworthy (e.g. is the UAVsuccessfully communicating with ground control?). During operation (e.g.task execution), the operator interfaces with the aircraft and overallUAS through a controller. The operator may control the UAV through thecontroller. In some implementations, a flight plan may be prepared bythe IUAS for the UAV and does not require control by the user. The IUASoperates until the task is completed or the user cancels the task. Thetask-based drone configuration and verification reduces the possibilityof task failure.

1. An unmanned aircraft system (UAS), comprising: an unmanned aerialvehicle (UAV); a processor running a UAS design module; a user inputdevice receiving user input indicating a selected task; a display deviceoperated by the processor to display an identifier for a UAS moduledetermined by the UAS design module for performing the selected task; aconnector associated with the UAS module; and the UAS modulecommunicatively coupled to the UAV via the connector.
 2. The UAS ofclaim 1, wherein the UAS module includes memory storing module dataincluding an identifier of the connector and a location on the UAV forpositioning the connector.
 3. The UAS of claim 1, wherein the UAS moduleincludes memory storing module data including one or more of: anidentifier of the UAS module, weight of the UAS module, powerconsumption by the UAS module, sensors included in the UAS module,number and location of connectors for attaching the UAS module to theUAV, lift provided by the UAS module, power provided by the UAS module,and mounting location for the UAS module to the UAV.
 4. The UAS of claim1, wherein the UAS module includes memory storing module data includingidentification of the UAS module and wherein the UAS design moduleverifies that the UAS module is communicatively coupled to the UAV viathe connector via communications with the UAS module via the connectorbased on the identification in the memory.
 5. The UAS of claim 1,wherein the UAS design module determines a second UAS module forperforming the selected task, the second UAS module including moduledata in memory, wherein the module data for the UAS module and thesecond UAS module further includes a module weight and a module-providedlift.
 6. The UAS of claim 5, wherein the processor further runs anautocalibration module to determine whether the module-provide lift ofthe UAS module and the second UAS module is greater at least than theweight of the UAS module and the second UAS module and if not to displayan error message on the display device.
 7. The UAS of claim 1, whereinthe UAS design module determines a second UAS module for performing theselected task, the second UAS module including module data in memory,wherein the module data for the UAS module and the second UAS modulefurther includes a power consumption value and a power provided value.8. The UAS of claim 7, wherein the processor further runs anautocalibration module to determine whether a summation of the powerprovided values exceeds a summation of the power consumption values andif not to display an error message on the display device.
 9. The UAS ofclaim 1, wherein the UAS module comprises one or more components fromthe group of: a camera, a sensor, a navigation element, a processor, awireless communication element, memory, persistent memory storing moduledata, a power source, a UAV fuselage, a payload, a stabilizationelement, a thrust element, a lift element, a display device, and aflight control device.
 10. The UAS of claim 1, wherein the UAS designmodule is adapted to determine a range for the UAV with the UAS modulebased on module data stored in memory of the UAS module and wherein theprocessor operates the display device to display the determined range.11. An unmanned aerial vehicle (UAV), comprising: a body with aprocessor; a first hardware module; a second hardware module differingfrom the first hardware module; a first connector for communicativelycoupling the first hardware module with the processor at a firstlocation on the body; and a second connector for communicativelycoupling the second hardware module with the processor at a secondlocation on the body.
 12. The UAV of claim 11, wherein the first andsecond hardware modules include memory storing module data that includesat least one value from the group of: a module identifier, moduleweight, module power consumption, included sensors, number and locationof connectors for attaching to the body, provided lift, and providedpower.
 13. The UAV of claim 11, wherein the first and second hardwaremodules comprise differing sets of one or more components selected fromthe group of: a camera, a sensor, a navigation element, a processor, awireless communication element, memory, persistent memory storing moduledata, a power source, a UAV fuselage, a payload, a stabilizationelement, a thrust element, a lift element, a display device, and aflight control device.
 14. The UAV of claim 11, wherein the first andsecond connectors are adapted to provide detachable coupling of thefirst and second hardware modules to the body of the UAV.
 15. A methodof fabricating a UAV, comprising: with an input device, receiving userinput selecting a task for the UAV; with a processor, determining a setof hardware modules for performing the task; displaying on a displaydevice the set of hardware modules, wherein each of the hardware modulesincludes memory storing a module identifier, a connector identification,and a connection location; and based on communications with the hardwaremodules via the connectors, determining whether all of the hardwaremodules have been communicatively coupled to the UAV.
 16. The method ofclaim 15, further including, when the determining of whether all thehardware modules have been coupled fails, displaying an error indicationon the display device.
 17. The method of claim 15, wherein each of thehardware modules comprises one or more components selected from thegroup consisting of: a camera, a sensor, a navigation element, aprocessor, a wireless communication element, memory, persistent memorystoring module data, a power source, a UAV fuselage, a payload, astabilization element, a thrust element, a lift element, a displaydevice, and a flight control device.
 18. The method of claim 15, whereinthe memory of each of the hardware modules stores a module weight and amodule-provided lift, and wherein the processor determines whether asummation of the module-provide lifts is greater than a summation of themodule weights and, if not, displays an error message on the displaydevice.
 19. The method of claim 15, wherein the memory of each of thehardware modules stores a power consumption value and a power providedvalue, and wherein the processor determines whether a summation of thepower provided values exceeds a summation of the power consumptionvalues and, if not, displays an error message on the display device. 20.The method of claim 15, wherein the processor determines a range for theUAV based on module data for each of the hardware modules stored inmemory of the hardware modules and wherein the processor operates thedisplay device to display the determined range.